I have already migrated multiple users with no issues, but this last user, once his mailbox had been migrated over to our Exchange 2013 SP1 servers, his Outlook client could no longer find the Exchange server.  He received the message that an admin has made changes that require them to restart their Outlook client.  Once he did that, he was presented with a message that Exchange was unavailable and that the server may be offline.  All other users, who also reside in the same subnet, are working just fine.

He can connect via OWA and his mobile device with no issues, it is literally just Outlook.  I logged on to the same machine where he is having the issue and was able to configure my account with no issues.  I removed his mail profile and recreated it with no success.  I then took it a step further and removed his local computer account and recreated it...still with no success.

I then had him log into a laptop with Outlook 2013 installed and he was presented with the same errors.  If I configure his Outlook profile manually, it will work just fine.  Also, if I migrate his mailbox back to an Exchange 2010 mailbox database, everything works just fine.

I still have hundreds of mailboxes to migrate and want to make sure this issue is resolved before proceeding.  Any information or other troubleshooting steps would be greatly appreciated.

I don't understand what you mean by, "If I configure his Outlook profile manually, it will work just fine," and why that's not a solution to your problem.

Hi,

Please create a new user in Exchange 2013 and check whether this new user can connect to Exchange 2013 with automatically account setup in Outlook or not.

If the new user can work fine with Outlook, it indicates the autodiscover service in Exchange 2013 should be accessable. The issue should be related to the migrated user. Then confirm whether the issue happens to all migrated users. Please do the following changes to have a try:

1. Open ADSIEdit.
2. Connect to the Configuration container.
3. Expand Configuration, expand CN=Configuration,DC=Domain,DC=com.
4. Expand CN=Services -> CN=Microsoft Exchange -> CN=Domain -> CN=Administrative Groups -> CN=Exchange Administrative Group -> CN=Databases.
5. In the right hand pane you will see a list of databases.
6. Right-click the listed database object -> Properties.
7. Check whether the msExchHomePublicMDB value is set to an unavailable value. If you see reference to the old database, please clear the value.
8. Click OK.
9. Check the rest of the databases to make sure that they are not populated in the same way.

Then create a new Outlook profile for the problematic user to check whether the issue persists.

Regards,

So I just did a migration of 300 users and 4 users had this issue and I can't for the life of me figure out what is going on.  If I enable OWA, the user can get to their mailbox, but Outlook will still not configure.  Again, everything worked just fine for 296 users...its just these 4.  Any ideas as to why Outlook can't configure itself?

That percentage sounds about right to me.  There always seem to be a few balky Outlook clients in any upgrade.